projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b3adfa8) | patch
unlock: Use deployment backing dir
authorColin Walters <walters@verbum.org>
Thu, 20 Mar 2025 16:47:48 +0000 (12:47 -0400)
committerColin Walters <walters@verbum.org>
Mon, 24 Mar 2025 22:24:31 +0000 (18:24 -0400)
commitd70febedfbd104a94ac7dee202b162998fd4e668
treebb7776a9c02d1bfe2bd8ea9dbe8d1ed129a4578atree | snapshot
parentb3adfa83ab61682dec6c3834678ca2e9eae43e03commit | diff
unlock: Use deployment backing dir

Closes: https://github.com/ostreedev/ostree/issues/3391
Basically it's not uncommon to make `/var/tmp` a separate
partition, but this constrains the amount of data that
can be written to `/usr` when unlocking.

Change things here to write to the deployment's backing
dir which is part of the same rootfs as the storage
and is lifecycle bound to the deployment, ensuring
it gets GC'd.

Signed-off-by: Colin Walters <walters@verbum.org>
src/boot/ostree-tmpfiles.conf diff | blob | history
src/libostree/ostree-sysroot.c diff | blob | history
src/libotcore/otcore.h diff | blob | history
tests/kolainst/destructive/unlock-transient.sh diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.